Please excuse the mangled terminology ;)
You have a Windows DNS server handling internal traffic for the yourco.com domain.
You want just the external website (www.yourco.com) to be ultimately resolved from a public DNS server such as your ISP's (e.g. should you ever change the IP address of your website you wouldn't have to update both your companies private DNS server and the public DNS records)
How can you achieve this using Windows DNS server?
When I run the Network analyzer at http://netalyzr.icsi.berkeley.edu/ it reports:
The resolver at could not process the following tested types:
Medium (~1300B) TXT records
Large (~3000B) TXT records
It does not validate DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Hide them.
Version: Microsoft DNS 6.1.7601 (1DB14556)
I have tried fixing the inability to resolve Medium and Large queries by setting MaximumUdpPacketSize to 4096 and rebooting (DNS Registry Entries). Changing that setting had no affect.
How do I fix both the record size issue and ability to validate DNSSEC while keeping all standard DNS functions working?
We host about 125 DNS forward-lookup zones on a Microsoft Windows Server 2003 DNS Server. We need to migrate to a new block of IPs and don't want to go through each zone manually. What's the best way to globally change one ip (1.1.1.1, for example) to another (2.2.2.2, for example) in ALL DNS zones and records?
I found the following message inside the DNS Server Event logs.
What I should do has been explained inside the message but not sure what exactly it means.
Log Name: DNS Server
Source: Microsoft-Windows-DNS-Server-Service
Date: 14.08.2011 11:30:57
Event ID: 414
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: WIN-EG75FS9C2F2
Description:
The DNS server computer currently does not have a DNS domain name. Its DNS name is a single-label host name with no domain (for example: "host" rather than "host.microsoft.com").
You might have forgotten to configure a primary DNS domain for the server computer.
Because the DNS server has only a single-label name, all zones created will have default records (SOA and NS) created using only this single-label name for the server's host name. This can lead to incorrect and failed referrals when clients and other DNS servers use these records to locate this server by name.
To correct this problem:
1) Click Start, and then click Control Panel.
2) Open System and Maintenance , and then open System.
3) Click Change Settings, and then click Change. 4) Click either Domain or Workgroup, and then type the name of the domain or workgroup you want the computer to join; the domain or workgroup name will be used as your DNS domain name.
5) When prompted, restart the computer.
After the computer restarts, the DNS server will attempt to fix up default records, substituting the new DNS name of this server for the old single-label name. However, you should review the zone's SOA and NS records to ensure that they now use the correct domain name of this server.
Event Xml:
<Provider Name="Microsoft-Windows-DNS-Server-Service"Guid="{guid-comes-here}" EventSourceName="DNS" />
<EventID Qualifiers="32768">414</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-08-14T08:30:57.000000000Z" /> <EventRecordID>159</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>DNS Server</Channel> <Computer>MyComputerName</Computer> <Security /><Binary> </Binary>
I need to change about 100 DNS records and IIS configurations on a Windows 2003 web server. The GUI doesn't accommodate it and the MS command line tools seem incomplete (for example: dnscmd cannot edit a record, only create). Is there a third party tool out there I can use?
Basically I just need to change one IP address to another.