search for: kdsdc

I have just set up a new AD and am having a little success with it, but DNS resolution is a little slow. I'm looking into why that is and tried an ns lookup for google.com and got the answer SERVFAIL on my AD server. The query was then passed to my next nameserver (google's own dns), which handled the query. Is this correct behaviour? I've not seen SERVFAIL before itadmin at

...: >> Name: google.com >> Address: 216.58.195.78 >> ;; Got SERVFAIL reply from 192.168.4.5, trying next server >> Name: google.com >> Address: 2607:f8b0:4005:80b::200e > > Is this on the DC or a client ? > > On my DC I get this: > > adminuser at kdsdc:~$ nslookup google.com <http://google.com/> > Server: 192.168.0.10 > Address: 192.168.0.10#53 > > Non-authoritative answer: > Name: google.com <http://google.com/> > Address: 216.58.204.46 > Name: google.com <http://google.com/> > Address:...

...> > Name: google.com > > Address: 216.58.195.78 > > ;; Got SERVFAIL reply from 192.168.4.5, trying next server > > Name: google.com > > Address: 2607:f8b0:4005:80b::200e > > Is this on the DC or a client ? > > On my DC I get this: > > adminuser at kdsdc:~$ nslookup google.com > Server: 192.168.0.10 > Address: 192.168.0.10#53 > > Non-authoritative answer: > Name: google.com > Address: 216.58.204.46 > Name: google.com > Address: 2a00:1450:4009:807::200e > > Rowland > > > > -- > To unsubscr...

...ress: 216.58.195.78 > >> ;; Got SERVFAIL reply from 192.168.4.5, trying next server > >> Name: google.com > >> Address: 2607:f8b0:4005:80b::200e > > > > Is this on the DC or a client ? > > > > On my DC I get this: > > > > adminuser at kdsdc:~$ nslookup google.com <http://google.com/> > > Server: 192.168.0.10 > > Address: 192.168.0.10#53 > > > > Non-authoritative answer: > > Name: google.com <http://google.com/> > > Address: 216.58.204.46 > > Name: google.com <htt...