Recently, I just purchased a domain from AWS by using Route 53. The problem is that I want to point this domain to a wordpress website that lies in Vultr host, but even thought I changed the NS record on Route 53 to Vulture's and test it by using https://www.dnswatch.info/, it still cannot open my website when I enter new domain to browser. I got little knowledge when it comes to DNS so please help ..
This is Vultr's DNS setting
and Route53 setting (I have changed the sensetive info)
I believe the issue here is you are attempting to add the Vultr Nameservers as NS records in Route53. So, Route53 would still be your primary nameservers.
Instead you want to specifically change over the primary Nameservers / glue records (separate UI / settings area than DNS records). See the final section on this page for details on how to do this -
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#updating-name-servers-other-dns-service
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.
I have an issue with my Plesk instance which really doesn't make sense to me.
I am creating a lot of subdomain for my clients on my main domain.
I don't handle any DNS on my server, service is disabled in Plesk and my 2 DNS servers for that main domain are my domain/vps provider ones (OVH).
I use then to create a subdomain as a zone DNS for each of my client in OVH backend, but know I chose to simply use a wildcard to avoid having 100s of entry.
Then I go to plesk and add a subdomain (vhost) with the associated folder where the subdomain (or domain) needs to go. It use to work fine but unfortunately now I have an error saying:
Error: Failed domain creation: Unable to update the domain data: The
serial number update limit was reached. No further change on the DNS
zone can be done today.
I really don't get it as, on my provider, I can create as many DNS zone as I want, and I really don't see the link between my server/Plesk vhosts/domains/subdomains and the DNS! I don't handle any DNS on my server and I thought creating a subdomain or domain on Plesk was just creating a vhost.
I am stuck on that one, would be great if any of you ever encounter that issue could help me.
PS: Couldn't find anything online ...
PS2: Called my provider and talked to me about SOA limitations, But again I can't see the link here. As the error is not when I try to create a DNS zone but when I try to set a new vhost.
This is a plesk bug know for me as PPPM-2590.
As workaround you can uncheck 'Use serial number format recommended by IETF and RIPE' on parent domain where you have a lot of subdomains or server-wide in 'Tools & Settings > DNS Templates > SOA record Template' and sync template with domains.
You can try this custom fix
Make sure that you have latest update #68
Backup original file:
cp /usr/local/psa/admin/plib/Dns/Zone/Abstract.php /usr/local/psa/admin/plib/Dns/Zone/Abstract.php.ORIG
Download https://docs.google.com/uc?authuser=0&id=0B7Nx66lufdvpSkxxeHpqaGtvWTg&export=download and place it to /usr/local/psa/admin/plib/Dns/Zone/Abstract.php
I am having difficulties getting my domain to point to my EC2 properly. I searched through a few third party guides online, and got slightly swamped in the official AWS documentation, but despite this I still cant get it to work.
Ive have Route 53 set up like this:
Type: A
Value: ??.??.??.?? (IP address)
Type: NS
Value: ns-1403.awsdns-47.org.
ns-1696.awsdns-20.co.uk.
ns-632.awsdns-15.net.
ns-431.awsdns-53.com.
Type: SOA
Value: ns-431.awsdns-53.com.
awsdns-hostmaster.amazon.com
And on my domain host I have the DNS Records set up like this:
Hostname: www
Type: NS
Value: ns-1403.awsdns-47.org
ns-1696.awsdns-20.co.uk
ns-632.awsdns-15.net
ns-431.awsdns-53.com
I think I am doing something fundamentally wrong. Firstly Im not sure if I got the Hostname part right on my DNS records. On the site it says .domain after the input box for the Hostname, which makes me think its a sub domain specifier. Am I right in thinking the # symbol works for no subdomain? (i.e. domain.com instead of www.domain.com)
Secondly should I remove the NS record set from Route 53, as its already specified in the DNS Records on the domain host?
Many thanks
There are two missing pieces here: telling your registrar to use Route53 instead of their own NS servers, and telling Route53 about your EC2 instance.
First, you need to set up your registrar. In this step you're telling the registrar to tell the global DNS system to look at Route53 for information about domain.com. Here's a quick tutorial for Namecheap and here's one for GoDaddy. Other registrars are similar, just google for YourRegistrarHere assign nameservers.
Second, to tell Route53 about your EC2 instance you should set an A record for domain.com within Route53 pointing at the elastic IP address that your EC2 instance is assigned. You should also create another A record for www.domain.com pointing at the same IP.
For your second question, as soon as you set up your registrar correctly the interface for creating records should just go away. You'll be managing all of your DNS records through Route53 instead.
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
I have a server that already has a domain, lets say mysite.com but i want to put another site on it with the domain mysite2.com.
So my questions are, how do i set up the nameserver settings.... My first domain i have listed
ns1.mysite.com
ns2.mysite.com
So would it work if i used:
ns1.mysite2.com
ns2.mysite2.com
for my new site?
Also, i have to set up "glue records". These are the ns1 and ns2 from the nameserver and provide the ip of my server. So for the mysite2.com would i use ns1.mysite2.com and then the ip would be for example 111.111.111.111/MYSITE2 ? Because the glue record for the first site is just 111.111.111.111.....?
Hope this isn't to confusing, i'm just new to this stuff and want to understand it a bit better and i don't want to mess my original site up in anyway.
thanks for the help.
Your DNS records don't have to be within the same domain as the one they host. If you are running your own DNS servers, they can live inside your primary domain. But if you're using another DNS provider like zoneedit.com or easydns.com, just use the hostnames they provide.
"Glue records" are the NS pointers that let the root servers find the DNS servers for a particular domain. For example, there might be:
mysite.com NS dns1.example.com
mysite.com NS dns2.example.com
mysite2.com NS dns1.example.com
mysite2.com NS dns2.example.com
Note that this is entirely different from where your domain's web site is served. For that, you just configure the DNS for each of these domains so that the IP address for the "www" host (and probably the domain itself) points to the same IP ... then you read your web server software's documentation on how to set up "named virtualhosts".
Are you clear on the distinction between DNS hosting and web hosting? If not, I can go into more detail.