• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 446
  • Last Modified:

DNS problem - urgent !

Help !

My fairly newly created DNS has stopped working. Not sure what I've done. Need help ...

1. Simple '20 user domain'
2. DC has DNS on it - clients use DHCP - 'A' records have been registering OK
3. The gateway is a GNATBOX which is working fine
4. The DNS fails the 'recurrsive' test
5. Forwarders are set to 'pingable' external DNSs
6. If I bypass our DNS using DHCP (set to external DNS's) ... all is well ... but I don't know what I've done wrong here

So, I need an expert to walk me through DNS testing.

Perhaps to add to the confusion, there are 2 NICS on this machine, a 192.9.200.10 address (for the subnet it is suppling) and a 10.10.1.100 address, so I can remotely use it from my office (i'm on another domain) ... I don't think this is having a baring, but it might.

Any help pleeeeeeeeeease

Thanks,

S.S.
0
SpencerSteel
Asked:
SpencerSteel
  • 5
  • 3
1 Solution
 
SpencerSteelAuthor Commented:
oooooooh...maybe the dual-nic is causing a problem ... i try to launch NSLOOKUP and get

"can't find server name for address 10.10.1.100"

S.S.
0
 
Nirmal SharmaSolution ArchitectCommented:
No Doule NIC has no problem for it. First tell me one thing why are you using other NIC. DNS can serve client request for any interface. You can list your NICs interface in DNS server property > Interface tab then you must restart DNS service. Check interface tab and let me know.

SystmProg.
0
 
SpencerSteelAuthor Commented:
Yeah - both are listed in interfaces.

I'm using 2 nics because (deep breath) ... I need to administer it from my subnet (10.10.1.0) and the router doesn't pass through my Remote Software (at the moment) ... so it's just so I can access it easily from this side of the network ... does that make sense ?

(It's chaos around here right now ... seat of the pants stuff)

Anything else I need to check ?

S.S.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
SpencerSteelAuthor Commented:
Solved ...

I went to the machine locally and DISABLED the 2nd card to my 10.10.1.0 network ... i restarted the services and it went off first time.

Although this is solved, this is a pain, as I can't use the 2nd NIC ... any idea what setting may of been wrong ? It seemed like the DNS wanted to default to the 10.10.1.0 nic for things like NSLOOKUP ... when it should really be using the 192.9.200. address ...

Thanks,

S.S.
0
 
SpencerSteelAuthor Commented:
oh god ! no it's still not working ... it's passed both tests on the DNS server though ... that must be progress ...

I really, really am in the wrong job.

*sigh*

S.S.
0
 
SpencerSteelAuthor Commented:
OK .. it's definately, definately, definately working now ...  *sigh*

I will just have to find a way around my dual NIC 'solution' which clearly is confusing the hell out of it

Thanks,

S.S.
0
 
Nirmal SharmaSolution ArchitectCommented:
<laughing>. No problem friend. When you are sure its working then close this question.

Thanks
0
 
Nirmal SharmaSolution ArchitectCommented:
Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now