For the PTR type records we use the full IP address again this is added backwards. Once you click finish again, check that all zones are running and that the sever is running. This time we use a command line option to tell it we are doing a reverse lookup, -x, and pass in the IP address. This section will get DNS and DHCP on Synology NAS working together.
If you use DHCP to automatically give out a valid IP address to a network attached device, probably from your broadband router or Wi Fi box, you will not be able to lookup hostnames to find their IP address as they are not registered with your shiny new DNS server. You will need terminal access to you Synology NAS, it can be turned on from the Control panel - Terminal & SNMP in the terminal tab.
Using a CNAME type record means if you more your mailserver and by default your blog to a different IP address you only need to update the one A type record.
You could however just have two A type records one for each name pointing to the same IP address.
You will only really need this if you have some local servers, computers or other devices that need to be accessed. If you need help installing the DNS package do not even try this tutorial you are not ready yet. Learn to swim before jumping into the middle of the river! This is where you configure the lookups, where you know the hostname and want to find the IP address. Note: I use a serial format of the date yyyymmddnn where the last two digits ‘nn’ are just a sequential number for changes I made by hand on a particular day. We also need one A type record for each server or device in our domain. we will need to setup mailserver and the media server running mythtv called mythtvserver.
Once installed and running you will find the DNS icon in the main menu. This serial number is used if you have a backup or slave DNS systems. The NS type record was created already when we created the forward zone. Use the example below to create the others as well.
Click finish to return back to the main DNS server window.
The CIT DNS servers will still be the primary server for the domain and will delegate the SRV record zones to the Windows DNS server.
If they are not set to that, you did something wrong. Point the DNS server setting of a device or PC to your new DNS server and use ping to try out the A, CNAME and MX records we created. This means if you perform the same lookup within a few minutes of each other the DNS does not actually do the lookup it looks in its cache first, it can do this quicker then performing the lookup. Any queries that cannot be resolved need to be forwarded to another DNS server.
If you are running Linux or another proper OS with a dig command you can use that with the full hostname. If not you did something wrong which needs to be fixed before you continue. You can use the following command to find the MX records for a domain. The DNS server will now resolve all our local hostnames to IP addresses. We do that by setting the values in the Resolution tab.
Follow these steps to integrate the Windows 2000/2003 Active Directory domains with Cornell's DNS servers while still supporting the Dynamic DNS capability needed for Active Directory to function properly.
The System Admin has to run local DNS server(s) under Windows on their domain controllers to handle the SRV records.