I have the following DNS settings for the site fls.net:
I am switching my domain registrar to know use the Zergio name servers, as opposed to Hostgator, to resolve the DNS. I would like all of our mail to go the same IPS listed in the above diagram.
When I try to enter the IP of the priority 0 MX record in my Zerigo UI I get the following error:
We are sorry but the Host could not be saved.
The following problems were found:
Data must be a valid domain name
My question is, If I am trying to route all the new Zerigo MX records I am creating for the domain fls.net to the old MX records with IPS 69.28.248.225 and 198.20.73.147 how am I to do that if the data only takes domain names?
If I put mailst1.fls.net. as the data for the MX record, how is going to know to resolve that address to the Hostgator mail IP, if I am now bypassing the whole hostgator name servers and using Zerigo instead?
So I didn't understand that MX Records just map to domain names, at least in the Zerigo interface.
So I just did the following
created an MX record which maps to mail.fls.net
And then created a mail.fls.net A record which maps to the Hostgator mail IP
Related
For eg. we wanted to search google.com (let us think that its an alias name), then we will lookup in DNS and get its canonical name which further helps to get the IP address. Why cant we just get IP address from alias name as it would also be unique.
It is not always guaranteed that alias name resolves to same IP address. And, there is a very good reason for it. Lets say person A is browsing google.com from country A. Google has it servers all over the world (for efficiency purposes). It is beneficial if person A requests are directed towards google servers in country A than towards some other distant location. Here where CNAME records comes into the picture. CNAME records are configured in such a way that google.com resolves to servers which are specific to country A. And another case where you get different IP for same alias name is when you fetch MX records (mail server records), for the same domain you can have different servers managing mails and web traffic.
The design of URL is for convenience. The convenience is that when we want to change the server IP, we don't need to tell all the users the new ip of the website. In other words, what we have done in server will make no change to users. That is the core thought in server design.
I changed DNS provider recently and I am trying to add DNS records to my new provider. However, I am unsure about how many records I should add.
My old nameserver had a whole bunch of auto-created records like "ftp.example.com", "cpanel.example.com", "_carddavs._tcp.example.com", "webdisk.example.com", "autodiscover.example.com", etc etc.
So my question is, can I just add the below TWO A records?
# ---> A Record pointing to my host IP address
www ---> A Record pointing to my host IP address
Any replies would be greatly appreciated!!
This question is akin to asking 'how many contacts do I need in my address book'
If you only have one friend, then a single record is all you need. (I'm ignoring the required SOA and NS records)
If you are going to have something talking to ftp.example.com then go ahead and add that record.
If you want to recieve mail on that domain, then you will need at least one MX record.
If you want to host a website at www.example.com then you will need to add a www A record. (or if you want to host a website at notwww.example.com, then add that A record)
Fill your DNS up with whatever you need it to have.
The reason for all of the already included options is that they lead off to revenue generating pages for whoever hosts your domain.
I created a domain at freenom.com
https://imgur.com/a/ClaXVLX
which points to my app at Digital ocean droplet.
and next day I created this domain I tested and it works.
that domain is 1) at printscreen above.
Now I want to create several subdomains, as I know that is possible to make:
site.com - domain
dev1.site.com, dev2.site.com - subdomains
But I do not know what must be entered in fields 2) and 3) ?
When I tried as at printscreen above I got error :
Error occured: Invalid value in dnsrecord
Which are valid values ?
Thanks!
A domain name (for use as websites etc.) should point at an IP address. There are several kinds of DNS records. Records for pointing at IP addresses are A records, as you have in 1). Other kinds are MX records for mail servers, for example.
If you want to create a subdomain, you want to create another A record, so simply choose A for the "type" field.
Alternatively, if the IP is the same as an existing record, use a CNAME record which points to another record, e.g.
Name Type TTL Target
dev1.site.com CNAME 14440 site.com
This says that dev1.site.com should use the same record(s) as site.com, so if you ever update the A record of site.com, it will automatically apply to all subdomains too.
I found the way to
add two A record
A www.dev2 IP (same ip of your original website)
A dev2 IP (same ip of your original website)
Setup 2 subdomains on the Freenom DNS:
The CNAME record type does not accept a IP number.
For the subdomains, use a CNAME, but make the target the # sign, which represents the root domain.
To be clear, this will make both subdomains point to the IP address of the A record you specified for the root domain.
If you want the subdomains to point to a different IP, then use an A record instead of a CNAME record.
i tried to search internet but not found answer.
On one domain name, in root and in a sub-domain name i have MX records pointing to the same mail server with same prios:
domain.com in MX 10 mail-1.com
abc.domain.com in MX 10 mail-1.com
Zone was released without any errors, and now from external DNS check when i DNS-reverse: abc.domain.com i get this result:
abc.domain.com IN MX 10 mx.abc.domain.com
Crazy, isnt it?
am i missing something here?
Maybe same MX servers cant be connected to # and sub-domain?
or maybe i should set different prios and it will work correctly?
or simplest: if MX is connected to root, there is no need to add it to sub-domain?
thanks for help!
MX record is a type of resource record in the Domain Name System that
specifies a mail server responsible for accepting email messages on
behalf of a recipient's domain
So answers to your points:
of course, mail servers can handle multiple different domains. I am certain that ASPMX.L.GOOGLE.COM is set as MX record for thousands of domains
priorities don't matter here, thyy are used in case you have multiple MX records for the same domain
you need MX for subdoman only if you intend to receive emails for something#sub.domain.com addresses
(Troubleshooting any issues/mismatch will be difficult without real domain name)
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