Tricky DNS Problem (Windows Server 2003)

Home Forums Server Operating Systems Windows Server 2000 / 2003 / 2003 R2 Tricky DNS Problem (Windows Server 2003)

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Avatar
    chief007
    Member
    #122773

    We have a VPN to another domain to access sites on their network. I didn’t want to edit the hosts file on every PC so created a Forward lookup zone (lets call it x.com). I entered all the hosts required. I added alias records to our forward lookup zone so we could use unualified names and it all worked fine…..

    Except we could no longer email them @x.com. I’m guessing because there was no MX record in the X.com forward lookup zone on our DNS. I know I could add these records but I would rather not have to duplicate public hosts.

    I’m assuming that DNS thinks the x.com forward lookup zone on our server should contain every record for x.com. Is there a way to tell it to also try the DNS forwarders if there is no record in the zone on our DNS?

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.