Windows Thread, DNS Problems... DCHP correct, DNS wrong in Technical; We are having a major headache with DNS here...
as you can se below the DNS ip is not matching ...
17th June 2008, 11:14 AM #1
17th June 2008, 12:30 PM #2
17th June 2008, 01:11 PM #3
Looks like your machines haven't registered the fully qualified domain. Try entereing lc1-03.wolverly.local into NSLOOKUP and see if it works.
Exactly the same result...
Looks like your reverse zone is borked. If you don't need it, delete it. You can recreate it later in your own time.
I paused the old reverse lookup and re-create it, I think now the reverse is working as it now has Pointers/entries building up in it.
But still doesnt help the fwd....
18th June 2008, 10:17 AM #4
This smells of DNS not having proper NS records set or perhaps the DNS records for your FWD zone aren't correct here.
Originally Posted by burgemaster
As for doing a NSLOOKUP on <your-pc-name> (not FQDN) - you need to have DNS search suffixes configured inside of Group Policy to make that little gem work, however it's not 100% important right now as even if you put in the FQDN - you still get nothing.
Let me throw you the entries we have here for one of our working zones.
(Same as Parent) Start of Authority (SOA) [###] dns.local, hostmaster.local
(Same as Parent) Name Server (NS) dns.local
dns Host (A) ##.##.##.##
### - Any number, usually relates to the number of updates the zone has had.
##.##.##.## - IP
Replace 'dns.local' with the FQDN of your DNS server.
Ensure that your DNS server has an A record in it's own zone.
Once done, Clear the DNS cache and then go to a local PC and type NSLOOKUP <your-DNS-server-FQDN> <your-DNS-server-IP>
This should then give you a positive lookup - I hope.
18th June 2008, 11:37 AM #5
Thanks guys, will have another look today !!
Will post back
PS. "NSLOOKUP says default server is 'unknown'. That's not good." <-- i think thats a vista thing
Last edited by burgemaster; 18th June 2008 at 11:40 AM.
27th June 2008, 09:21 AM #6
i think i may have found the problem, when i did a "netsh dhcp show server" to list all the DCHP servers (we only have one) i was getting 4 authorised dchp servers !!!
one was completely wrong, incorrect name to ip address, other 2 were on other servers which have not got dchp or ever have on them..
anyways i have cleaned it up and now I only have DC2 as the auth DCHP server.
Fingers crossed this will sort it out
Thanks for the help
27th June 2008, 09:53 AM #7
Is there a PTR record in the reverse lookup zone for 10.50.4.21 is it a DC?
Did you have any 9x machines in the past?
27th June 2008, 11:05 AM #8
Start with the simple stuff, in DHCP check your scope options and make sure you have entries for DNS Servers and DNS Domain Name. While your there check the DNS servers listed are correct and actually are DNS servers (even consider pointing it to 1 DNS for now).
Once thats done, see whats changed and if its worked then move on to the DNS if not.
As others have said check you have your name server(s) listed for your forward lookup (right click on the domain name in flz - properties) and ditch the reverse zones and try again.
Thanks to CHR1S from:
dwimorberg (21st June 2011)
By tosca925 in forum Windows
Last Post: 6th October 2007, 09:46 AM
By leon in forum Wireless Networks
Last Post: 20th September 2007, 03:53 PM
By iceman in forum MIS Systems
Last Post: 8th April 2007, 02:36 PM
By Cyber-Dude in forum Windows
Last Post: 26th May 2006, 10:01 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)