[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Reopen][Solved] Re: Post installation network problem



Hi Petter,

I tried that with 10.0.0.1, 185.150.99.255 and, to go safe, 8.8.8.8
No effect. My ISP (ewetel) doesn't tell anything about DNS's.

And, with dhcp disabled on the router, WLAN- and LAN-clients as well as DI of the network-installer work fine with 10.0.0.0/8 IP address, default gateway 10.0.0.1 and DNS entries 10.0.0.2, 10.0.0.1 and 185.150.99.255

Only after installation tjener has replaced the three DNS's by one: 127.0.0.1 and get's no contact outside the LAN. If I replace the entrie 127.0.0.1 in /etc/network by 10.0.0.1 I get outside, but gosa isn't useable from the LAN.

So my approach would be to get the named three DNS's in /etc/resolv.conf, but I have no idea where to force that.

Kind regards

readU
Frank

Petter Reinholdtsen:
[Frank Weißer]
the dhcp server on gateway (FRITZ!Box 7490) was definitely stopped
before installation and stayed so. I installed from the netinstall image
by entering network configuration manually when the automatic
configuration failed due to missing dhcp server. That's the problem; why
are urls resolved during installation but not after it?

Perhaps your ISP block direct DNS lookups, so you need to tell the main
server DNS to forward its lookups via your ISPs server, ref

   If generic DNS traffic is blocked out of your network and you need to
   use some specific DNS server to look up internet hosts, you need to
   tell the DNS server to use this server as its "forwarder". Update
   /etc/bind/named.conf.options and specify the IP address of the DNS
   server to use.

in <URL:https://wiki.debian.org/DebianEdu/Documentation/Buster/GettingStarted >.
Perhaps you can extend the text to make it easier to discover for the
next reader?



Reply to: