MS DNS Query

[Hulkster]

I have a AD Domain network..for the sake of example it's abc.com

We run AD integrated DNS as part of this

Now, recently we've had a requirement to set up a VPN to a supplier and we want to access their hosts and naturalyl DNS would be the easiest solution

Before I go on I will say that I am more experienced with BIND dns than MS AD integrated, so I may just be missing something.

Anyway, in testing, it keeps appending the parent domain suffix

How can I make it such that if i ping hosta.xyz.com that it takes this as the FQDN and doesn't associate it with our parent domain?

Is this a valid config?

As an aside, if we for example have records for hosta.xyz.com and hostb.xyz.com and we have the zone for xyz.com on a local DNS server...will the server forward a request for say www.xyz.com or will recursion not be performed when a DNS zone exists on a local server?

I hope that's clear!

Cheers

 

[Hulkster]

Ethos - thanks for your help and apologies for the late reply.

I had looked at a stub zone - but is it true to say that for this to work we need to add their DNS server IPs to this zone (as NS records)?

This would be a handy scenario - but the remote site don't want to open UDP port 53 through their firewall and don't want us using their DNS servers (they actually provided the HOSTS file).

Ideally we need to resolve it internally (and by resolve i mean both DNS lookups and the overall task )

Another thought I had was to set up a standalone DNS server, maybe runnning BIND, maybe MS, then set up a stub zone pointing xyz.com to that server, and then that server dish out the lookups. This however seems inefficient to me?

In your scenario 1 - I had tried the trailing dot and it didnt seem to want to play ball on my test box. In this case was it just adding a regular forward lookup zone? I did this, setting a primary zone and turned off dynamic updates. This would seem a logical option, if it's a valid one?

Ta!