DNS problem in a non-Virtualmin box

6 posts / 0 new
Last post
#1 Tue, 08/12/2014 - 13:29
bislinks
bislinks's picture

DNS problem in a non-Virtualmin box

I have setup a CentOS 6.5 box with public IP assigned to me by my ISP. (Virtualmin not installed)

I am able to access it by it's public IP (DHCP assigned per ISP requirement) but cannot access it by it's host/domain name.

Details.

Public IP: Public IP HostName: ns1.domain.com OS: CentOS 6.5 (Final)

cat /etc/resolv.conf search domain.com nameserver ISP provided Primary DNS nameserver ISP provided Default Gateway nameserver 127.0.0.1 domain ns1.domain.com

tracert ns1.domain.com (Executed on a windows 8.1 PowerShell) Tracing route to ns1.domain.com [IP] 1 * General failure Trace complete

nslookup ns1.domain.com (Executed on the box as root) Server: ISP Primary DNS. Address: ISP Primary DNS#53 Non-Authoritative answer: Name: ns1.domain.com Address: Public IP.

cat /etc/hosts (Executed on the box as root) 127.0.0.1 localhost4.localdomain4 localhost ::1 localhost6.localdomain6 localhost Public IP ns1.domain.com ns1 Public IP ns2.domain.com ns2

Would greatly appreciate any help.

Please ask for further details if needed.

Tue, 08/12/2014 - 14:32
andreychek

Howdy,

Well, you mentioned that Virtualmin isn't installed on this system... so for the domain name you're using, where is the DNS setup for this domain?

Normally, Virtualmin is what you'd use to configure the DNS. If Virtualmin wasn't used for that, that means the DNS would either need to be manually setup on that server, or hosted elsewhere.

You mentioned something about "ISP provided DNS" -- if the DNS for this domain is hosted at your ISP, that may mean there's a problem with their DNS records.

You may want to go to intodns.com, and have that run a DNS report to get some more details on what the issue is.

-Eric

Tue, 08/12/2014 - 17:18
bislinks
bislinks's picture

The 'ISP provided DNS' is actually the IP provided by the ISP for primary DNS and has nothing to do with the actual domain name service.

Yes, I have installed bind 9.8 (and am learning/working on it) on the box.

Will check/work with intoDNS, thanks.

Business Impact Solutions Computer Repair, Web Hosting, Web Design, and Web Development

Wed, 08/13/2014 - 11:29
bislinks
bislinks's picture

I am getting "Error: nameserver did not respond" from intoDNS for the PublicIP.

Details: DNS servers responded ERROR: One or more of your nameservers did not respond: The ones that did not respond are: 108.90.217.137 (which is the public IP for ns1.find-where.com)

How do i make ns1.find-where.com to be the authoritative server? Appreciate any help....

Business Impact Solutions Computer Repair, Web Hosting, Web Design, and Web Development

Wed, 08/13/2014 - 13:01
andreychek

Howdy,

Well, it sounds like BIND either isn't running on that IP, it isn't listening for remote connections, or it's firewalled off.

The next step would be to review your BIND setup, and the firewall setup, and determine why BIND isn't accessible remotely.

-Eric

Thu, 06/29/2017 - 15:39
scotwnw

IS the Name server listing at your registrar for "find-where.com" showing "ns1.find-where.com"?

Topic locked