Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have domain in one company, with an specific NS entries, but I don't want changes the NS entries.

The server is in another company with public IP.

If I want to point from my domain to the server, is enough with adding an A record into the domain company, that A entry would point to my public IP.

Is that OK?

How long it takes the changes?

How can I trace the A record propagation?

share|improve this question
The what server? DNS? HTTP? SMTP? FTP? – JdeBP Jul 7 '11 at 9:43
@JdeBP: Does it matter? The question is about DNS A records. – Iain Jul 7 '11 at 10:14
Of course it matters; and no the question is not. You haven't read the part of the question that asks whether adding A records is the "OK" thing to do in the first place and have just leapt in with the assumption that it is. – JdeBP Jul 7 '11 at 10:21
I'm missing something in that "how it matters" part...DNS doesn't control what ports you have open. If I have and want to ftp to it, I just ftp to, and if I want to hit the web server, I open – Bart Silverstrim Jul 7 '11 at 12:09

Use your domain companies tools to create an A record that points to the public IP address of your server. The changes can take quite some time perhaps up to 72 hours for global coverage but would generally be less. You can try tools like this to see how your A record is propagating.

share|improve this answer
I checked the propragation as you said, but how can I see, but is already progated for the old IP, how can I be sure that the new IP is ready for being propagated? In my case I adde so. A ip. Is that right, did not touch the ns servers. – arrrrgv Jul 7 '11 at 9:26
If you change the IP address as it propagates you should see it change in that tool. – Iain Jul 7 '11 at 9:30
The new IP once changed is propogated according to individual caching configured on other DNS servers. You have no control over that. It can take anywhere from immediate (if you're querying the servers on which the changes were made) to a couple days for worldwide propagation. Make the change on the authoritative server and it goes out; you don't "commit the change," so to speak. – Bart Silverstrim Jul 7 '11 at 12:11
Come on guys. DNS doesn't propagate. Stop propagating the DNS propagation idea. – joeqwerty Jul 8 '11 at 13:37
@joeqwerty that is a semantics discussion more suited to :^) – Iain Jul 8 '11 at 13:52

Adding a new A record for a new domain (host) should propagate quite quickly. Initial queries will go to your nameserver rather than caches. Changes to that domain will depend on the TTL for the domain.

There may be some delay with synchronizing the nameservers, but many setups use notify. This will speed things up.

The main problem will be possible negative caching. This should not be much of a problem, as noone should have been looking for the domain.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.