Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

DNS Structure

Just wanted to run something by the community.

Using fakeIPs for the example:

ISP IP: 192.168.2.1

Our IP Currently: 172.16.0.1

Our New IP Range: 12.18.0.1 to 12.18.5

Using Cisco IS 12.4T on 871

------------------------------------

Currently configured DNS

FEQDN TYPE RECORD PREF

A 192.168.2.1

ftp A 192.168.2.1

remote A 172.16.0.1

webmail A 172.16.0.1

MX remote.domainname.com 10

pop3 CNAME pop3.isp_server.net

smtp CNAME remote.domainname.com

--------------------------------------

Proposed Solution during migration

FEQDN TYPE RECORD PREF

A 192.168.2.1

ftp A 192.168.2.1

remote A 172.16.0.1

remote1 A 12.18.0.1

smtp A 172.16.0.1

mail A 12.18.0.2

MX 172.16.0.1 10

MX 12.18.0.2 15

webmail A 172.16.0.1

pop3 CNAME pop3.isp_server.net

Final migration (not during testing) - change the webmail A record to 12.18.0.3

Any suggestions - will this allow me to keep current things working and have a working alternative when testing the new router?

4 REPLIES
New Member

Re: DNS Structure

I don't fully understand the problem nor the proposed solution to it. If you can explain in more detail what the goal is, I could better respond.

If it's just about the mentioned "webmail" A record, changing it after you changed the IP on that system will work. And of course the MX record(s) need to point to vaild mail servers.

However, keep caching in mind. I recommend you examine the current TTL and lower it to e.g. 5 minutes / 300 seconds before the change. Otherwise the old IP address continues to be used if cached and you have no way to control this if it's your external DNS.

New Member

Re: DNS Structure

Scenario:

Moving from one DSL package to another. New package gives us 5 statics. we now have our own managed router, not just a pass-tru provided by ISP.

We have two circuits installed, I am trying to configure the 871 router we purchased to work so that on migration day, swap out the old and move in the new.

I currently have outbound communication working. I can VPN etc inbound - just don't have mail working inbound. I also can't get https://webmail.domainname.com to work with just the IP's. This may be more an issue with how OWA is setup (might recognize host headers only - not sure).

I wanted to modify our current DNS so that it will allow me to swap after hours to do some testing. Especially when it comes to mail.

I thought by adding the extra MX record to point to the new IP with a different priority number - that when I swapped it would not get a response on MX 10 and go to MX 15.

It is external DNS, so I do not have access to Time to Live values. So caching will be an issue?

I have another post for telnet (see Exchange and OWA recent post) - I was trying to troubleshoot and make sure exchange would still work inbound using the ip address.

Regards,

Chris

New Member

Re: DNS Structure

Thanks, Chris.

Just to get you right: You are running a DNS server already and have the domain you hold delegated to it?

Usually at least two DNS servers are required, so you either have two on your site or you specified one at your ISP or any other location. Make sure you update the IP address information there, too.

The TTL values are specified in the SOA record, just on top of your configration:

@ IN SOA nameserver.place.dom. postmaster.place.dom. (

1 ; serial number

3600 ; refresh [1h]

600 ; retry [10m]

86400 ; expire [1d]

3600 ) ; min TTL [1h]

So lowering the value there will do the job. If just some entries would change, you could even change the TTL for just them. But in your case it makes sense to me to lower it for the whole zone. If it's an hour, you could live with it, if it's several days, then rather not I suppose.

If your DNS is managed externally altogether, ask them to lower the TTL for your zone or ask at least how long the TTL is. If it cannot be changed - for what reason ever - you might loose (inbound-) connectivity, in worst case as long as the TTL currently set.

You can add the extra MX record, that will work. However, make sure to remove the obsolete one as soon as you have done the change.

PS: A link worth to read: http://www.ducea.com/2006/05/21/moving-your-website-to-another-server-tune-your-dns-for-minimum-downtime/

New Member

Re: DNS Structure

Some of this is coming back to me.

Yes, our DNS are managed by our ISP

We use internal (SBS 2003) server as our local dns that forwards requests to our ISP's DNS server.

A dig of our domain name shows the following

86400 IN SOA ns1.meganameservers.com. postmaster.meganameservers.com. 2008081217 86400 3600 3600000 86400

Looks like 1 day for expiration.

So,let me see if I understand this correctly. If I add the MX records now as

MX 10

MX 15

smtp A

mail A

In rougly 24 hrs I could switch the connections (power of unplug and plug!) and then send a message from an external source.

It should not be able to send to the MX record with the lowest priority - so will send to the next MX record.

How do the smtp and mail references apply to inbound mail exactly?

158
Views
0
Helpful
4
Replies
CreatePlease to create content