I have my system up and running and can browse the web no problem.
I am sat on a Windows Domain network (haven’t surrently got Domain Membership working though). For some reason, I cannot ping my domain server through the hostname server.mydomain.local, however I can ping the address 192.168.200.200. I have the Domain server (192.168.200.200) as my DNS server (the only server…)
Why is this not working? I can’t understand it! I have a good knowledge of setting up Windows servers and know it works properly…
I just can’t understand why I cannot ping anything by hostname on my local network… External is fine! The names obviously resolve OK as shown by my nslookup output above!
Been cracking my brain on this one… you seem to have set all there is to set.
You could install Wireshark to have a sniff whats happening with the packets…
That thing concerning .local domains ist the one about multicast dns.
If you put mdns off in /etc/host.conf this point is solved.
So there has to be another problem.
Im also using a .local domain and everything is working fine since ive added the mdns off line.
Hey, just dropped by in the hope of finding a solution because I have exactly the same problem. I am using my trusty Novell server (so no WINS or domain authenticaton to worry about) running DHCP and DNS. named is configured as authoritative for the local domain and forwards other queries to my ISP’s servers. This works for eveything else on my network apart from my newly built OpenSuse 11 box which can browse the web (all updates downloaded and installed) ping anything by IP address but cannot resolve local doamin names. I am using a xxx.local domain internally. nslookup find the DNS server and resoves the local deices successfully.
>
> Hey, just dropped by in the hope of finding a solution because I have
> exactly the same problem. I am using my trusty Novell server (so no
> WINS or domain authenticaton to worry about) running DHCP and DNS. named
> is configured as authoritative for the local domain and forwards other
> queries to my ISP’s servers. This works for eveything else on my network
> apart from my newly built OpenSuse 11 box which can browse the web (all
> updates downloaded and installed) ping anything by IP address but cannot
> resolve local doamin names. I am using a xxx.local domain internally.
> nslookup find the DNS server and resoves the local deices successfully.
>
> One of the oddest things I’ve seen . . . .
>
>
jmangan;
Are your local zones static or dynamic? If dynamic they need to reside
in /var/lib/named/dyn (By default Bind runs in a chroot jail,
see:/usr/share/doc/packages/bind/README.SUSE)
Check your named.conf for syntax errors:
In a terminal window su to root and run “named-checkconf” [no quotes]; this
outputs syntax errors, if none exist there is no output.
check your zone files using “named-checkzone <zonename> <filename>”
See: man named-checkzone; named-checkconf for details. Look at some of the
material in /user/share/doc/packages/bind
This is not a problem with the DNS server (which is not running on the Suse box). Every other device on my network picks up its configuration from DHCP and manages to resolve local and external names using the DNS server. The only box that doesn’t do this is the newly-built Suse box which does use the DNS server to resolve external addresses but will not resolve local devices either expressed as hostname or hostname.domain.local
From scratching around I thought it was worth looking in /etc/nsswitch.conf and I discovered in the hosts section that mdns_minimal [notfound=return] was placed before ‘dns’. From my understanding this would mean that dns would never be accessed (although external addresses must be found via DNS). I tried moving dns to the front of the queue but it didn’t make any difference.