My client has a website at exampleA.com, but want their new domain name exampleB.com to point to the server that hosts exampleA.com.
They have certain emails setup with exampleB.com...so I want to avoid changing the name servers, in case I mess with these settings (I don't know all the info yet).
If I simply want exampleB.com to point to a different server, what DNS records should I change? I have a static IP for the server.
Is it just the A record I need to modify? I'm not good with this DNS malarkey.
Thanks for your help.
Mikey.
Yes, just update the A record. You may have to update the web server config file on exampleA.com server to listen and serve the requests for exampleB.com.
If the static IP address you have is in IPv6 format then you would have to update the AAAA DNS record.
Yes, by changing A record in the domain account will solve the problem. In this case, you do not need to change the nameserver in the domain account
Related
I have access to a Godaddy account where the company has all their domains. One of those I need to point to another web server running Apache. The person that used to work here before me solved this pointing to the new server IP using the record:
A # the.ip.addr.ess 1 hour
and in the webserver end I get it with Apache and as far as the webserver goes, it runs flawlessly. I even have some subdomains using the same A record structure.
But...now I have two issues. First, I lost email reception. I can send via smtp and webmail but anything sent to my domain gets bounced back after 24 hours, even if sent to an alias or forwarder.
The second issue is that I need to verify the domain with Firebase and even thou I created the TXT record, it cannot be found by Google. I'm sure it's because of the same reason.
What can I do? I understand a little about DNS and records, but not enough for this. I just want all html traffic to reach my webserver as it is now and keep the emails and other domain services working as they were.
As contacting Godaddy support, they said it is not their purview as it is external. I think they just don't know. Go figure.
Are you using GoDaddys NameServers? If not and these are pointing elsewhere no matter what DNS records you set in GoDaddy won't be picked up during DNS lookips. This may explain why the TXT record verification is failing. However if this was true changing the A record wouldn'd disrupt DNS.
# just means the root domain so no subdomain/prefix, mydomain.com.
www is a common subdomain used so you could have an A record which like:
A www the.ip.addr.ess 1 hour
so www.mydomain.com would resolve to the.ip.addr.ess
MX records are used to direct emails to your mail server. Make sure this is pointing to the mail server. If it's pointing at your A record then updating the A record will disrupt this.
Set the MX record to point to the.ip.addr.ess rather then mydomain.com, or an A/CNAME record other then your root domain (which you are updating)
Other considerations may need to be taken, if you have an SPF record (TXT record) this may also need updating, depending on it's current value.
I finally found what I had to do. I needed an A record named 'mail' pointing to the original Godaddy server IP address.
A mail my.ip.add.ress. 1 hour
Thank´s for all the help.
[www.dyndns.com] is a site which gives us internet service,
If I use their service and get a domain name with an i.p.
Their server will transfer the domain name to 1.2.3.4 when someone browse it.
what did they do at the back? how can they do this?
can I set up a server like that?
Refer to this link you will find you answer there.
http://computer.howstuffworks.com/dns2.htm
If you make you question clearer I could provide a better answer.
If you wish to create a local DNS on your system I would suggest you make alterations to your hosts file. Located at C:/Windows/System32/Drivers/etc in windows system.
The order in which DNS names are resolved is:
HOSTS configuration file
The DNS to which your computer is confugured
The HOSTS file has the highest priority so you could override the DNS server by configuring an IP in your HOSTS file.
Ok, in a nutshell, for my own reaons, I am trying to "build" a solution that extracts my DNS from the location / company where my webserver is located. I need to be able to make DNS changes on the fly for my domains. I have nameservers set-up for the webserver, on the webserver. I basically want to know if I can point my domain registration DNS details, to lets say, a DYN.com dynamic DNS address, and have that dynamic address setup to just forward all traffic onto my nameservers on the webserver.
This way, I can change the dyndns "pointer" if you will, to any other webserver/nameservers immedietly should the need arise.
P.S. I know a dynamic address probably won't work, and If I have to go for a paid up service with DYN, thats fine, but I don't want to create all the records on DYN. I just want it to forward any requests to the actual ip of the name server on the webserver.
I.E.
Domain NS1 -> Dyn.com Record 1 (no specific domain records) -> ns1.mywebserver.com
Domain NS2 -> Dyn.com Record 2 (no specific domain records) -> ns2.mywebserver.com
Can this be acieved, if not, do you get what I am trying to do, and are there other ways of doing this?
I ideally don't want to create a dedicated linux VM somewhere to manage the DNS.
Thanks in advance.
I think my other question, posted after this one, solves this question.
BIND . Registrar says it cant find the nameserver. nslookup shows the domain is being handled by bind
Cheers
How can you test CloudFlare without changing your domain's name server?
I would not want to change my domain's name server and wait hours for propagation only to find out there is a issue with the DNS settings.
Can you spoof a nameserver or something on a local hosts file?
Yes, you should be able to test before you change your name servers. Here's what to do:
Signup at https://www.cloudflare.com/sign-up and complete the signup through Step 4 when you're asked to update your name servers.
Note the two name servers you are provided which will be in the format [name].ns.cloudflare.com.
From a terminal, do a lookup to get the IP addresses your domain has been assigned. In Linux/Unix it'd be: dig #[name].ns.cloudflare.com yourdomain.example
Repeat step 3 with all the subdomains you want to check.
Update your localhost record to resolve the domain(s) to the IPs you found with the lookup.
Browse the site from the same machine where you did the localhost update and traffic should pass through CloudFlare.
While this will work for a while, after 24 hours CloudFlare's system may detect that your name servers haven't updated and, in some cases, may return an error. However, this technique should allow you basic testing before you update your name servers.
To save future users from some headache, the above answer doesn't work anymore: https://community.cloudflare.com/t/ip-on-cloudflare-nameserver-is-not-masked-despite-orange-cloud/76137
From my understanding, you now need to change your nameserver.
everyday i get following email from the cpanel, i dont know what it means and in current configuration, i have a one ip for a ns1.nameserver and one for ns2.nameserver but top level domain nameserver is mapped to one ip address. but there is no way to add a another A record to there (i dont knw how) or i want to disable this notice out, since still all works fine in the network...
The hostname (nameserver.com) resolves to 67.xxx. It should
resolve to 67.xxxx. Please be sure that the contents of
/etc/hosts are configured correctly, and also that there is a
correct 'A' entry for the domain in the zone file.
Some or all of these problems can be caused by /etc/resolv.conf
being setup incorrectly. Please check that file if you believe
everything else is correct.
You may be able to automatically correct this problem by using the
'Add an A entry for your hostname' option under 'Dns Functions' in
your Web Host Manager.
Two ways to resolve the issue.
Add the correct A record for the IP and Fully Qualified Domain name
Per cPanel it is not suppose to function behind a NAT though as many have found this does in fact work. So you can "Fix" or stop this message by going into the contact manager and disable the “Ip address dns check” option
You need to make sure that you have properly added A record for your hostname and assigned it to IP address of your server. For example, if your server hostname is xyz.abcd.com then you need to add xyz A record in abcd.com DNS zone and point it to your server IP address.