I have a domain,
www.xyz.co.uk
now I would like to point for example,
www.data.xyz.co.uk to the ip address of my server(digitalocean)
So far what I did is, I have created a hostname on dns managementconsole of godaddy, with data.xyz.co.uk and pointed that to my ip address.
I am little confused wether that is it or I need to do more on my server ? Secondly when I do ping data.xzy.co.uk in terminal I get unknown host response.
Could somebody points me in right direction.
I manage to get the resolved the issue by adding A record in DNS settings of my hosts account and pointing that record to a desired Ip.
Related
The other day I was trying to RDC from my work laptop to work desktop using my PC's hostname but it could find the desktop. Later on I tried with my desktop's IP which worked. Both the time I was on premise and was connected to the network physically.
I could RDC every other computer in our network.
After my research, I checked firewall was disabled, flushed and re-registered dns etc. Everything seems to be in order. However, when I tried to do reverse DNS lookup it didnt work for my desktop.
After that my IT guy and I checked everything on the AD server and there was no entry for my hostname or the IP. So we manually added the dns record which didnt work either.
Following is the note from IT:
AD / DHCP on a server on a different subnet DNS on another server on
the above subnet
The Pc is on a VLAN again different subnet. The Cisco Switch controls
the VLAN but talks to DHCP server for scope
Even adding the A host on forward lookup manually can’t resolve using
hostname for ping / mstsc. Both work for IP so deff DNS issue.
Tried to ipconfig /release and renew after giving a different PC the
IP address that was originally assigned to this one thinking it would
force DNS to update.
There is no entry for the IP or the Hostname in DNS even when the IP
changed after a renew. The firewall on the PC is off. However there is
the entry in the DHCP address lease table.
Tried flushDNS and ReregisterDNS.
If anyone could point me to the right direction here I would be grateful. Also, if you need further information please let me know.
Thanks
This is not the correct forum for this question. However, I can point you in the right direction.
Your correct that this is a DNS issue (so it seems).
The entry that is missing is from the host you are trying to reach (not the client that your trying this from).
Make sure all of the systems are using the same DNS servers. Make sure the DHCP Client Service is running (even if IP address is hard coded) as that is what actually records the the host name and IP address in DNS.
It sounds like you have the routing set up or you would not be able to do it by IP address.
Is the DNS zone in AD set up to allow dynamic updates? Do you have the domain name being sent out via DHCP?
Windows will (but not always) try to find a host by DNS and will fall back to a broadcast for the PC name. This might be why it works from one VLAN, and not from another.
I got WHM on our VPS and already set up some websites in it.
Usually, I only need to create new Account, fill out the form (domain name, setting, etc).
Then change the nameserver on the registrar's website, then wait for max 48 hours.
Then the website is live.
But now the website is not live yet. I have been contacting the hosting support, but they do not respond quick.
Could you guys please let me know what should I check to identify the problem?
Thank you!
First of all you have to check if you WHM hostname is a valid hostname and then if the hostname points back to the WHM server ip. Then you have to check with a tool like intodns.com if you DNS zone for the domain is correct and if the domain name points back to your server's ip. If you can, please post your domain name (the one that is supposed to load from your WHM server).
If I ping my OpenShift application I see some IP like this
ec2-11-22-33-44.compute-1.amazonaws.com [11.22.33.44]
Can I be sure that my IP is 11.22.33.44 and I can use it for A record in DNS settings?
In which cases this IP is changed ?
Never seen this inforamtion. All articles claim that only CNAME may work.
You should never use an A record to point to your OpenShift application with an external domain. That IP address can change at any time for outage or maintenance reasons. You should always use a CNAME to point your domain name to your application url of the format app-domain.rhcloud.com
Just found an answer.
This was not just my own IP.
Several sites have this IP too.
http://www.bing.com/search?q=IP:11.22.33.44
I have Static IP, i would like to access website using static IP as well using domain name.
I have below DNS entries to for my domain, i am not sure what setup i need to do to make it works.
when user access my site using domain name they should be able to access. Also when someone want to access using IP address they should be able to do that.
www 14400 IN CNAME example.com
example.com 14400 IN A 50.63.147.111
If anybody have idea please let me know.
Thank you
Regards,
Mona
If you can't access your IP address, then it isn't because of your DNS. DNS stands for domain name system and translates domain names TO IP addresses. Thus, you must already have a reachable IP address for your A record to be meaningful. Make sure that you've configured your server correctly (Apache?) and that the necessary ports are open in your firewall (iptables).
Check that your domain registrar is pointing its name servers to the authoritative name server (the server with your zone file) for your domain.
I have a domain registered at godaddy [www.example.com]. And i have a free hosting at Binhoster.
I want to point my domain to Binhoster's FTP server where my pages are hosted.
I googled this and I was instructed to change my nameservers of godaddy to Binhoster's nameserver, then add the FTP IP in the A-Record.
But I, without changing the nameservers, Added the A-Record to point to Binhoster's and added a custom domain at Binhoster's [www.example.com to point to public_html] and its working. I'm currently using my original nameserver. Then why is it instructed to change nameservers everywhere. Is it mandatory ??
You may want to reach out directly to Binhoster to see why they suggest to change your NS. This may be because the IP address could change. If an IP address changes and you control the DNS, you will need to be notified and subsequently update the A record IP, whereas if you pointed your NS the IP may be updated automatically at the host.
Ultimately, as long as you point your A record to the host, you should be fine.