×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

DNS not resolving

DNS not resolving

DNS not resolving

(OP)
Hello.

I have configured a dns server to resolve pathwayschurch.com. The domain is registered and configured to point to ns1.pathwayschurch.com - 67.117.134.134 as the primary and because it is required through netsol, I entered my name server ns1.gigdev.com - 64.81.61.196 as the secondary server. I can not resolve www.pathwayschurch.com nor server01.pathwayschurch.com but I can resolve ns1.pathwwayschurch.com. I can resolve successfuly locally on my windows 2000 server which is the dns server. I forgot to mention that I can not see the mx record when I do an nslookup.

This is what I get when I run the following:

C:\>nslookup pathwayschurch.com

Server: ecdc2.esuhsd.org

Address: 170.91.1.103

DNS request timed out.

timeout was 2 seconds.

*** ecdc2.esuhsd.org can't find pathwayschurch.com: Non-existent domain

C:\>nslookup

Default Server: ecdc2.esuhsd.org

Address: 170.91.1.103

> server 67.117.134.134

Default Server: adsl-67-117-134-134.dsl.snfc21.pacbell.net

Address: 67.117.134.134

> set type=any

> pathwayschurch.com

Server: adsl-67-117-134-134.dsl.snfc21.pacbell.net

Address: 67.117.134.134

Non-authoritative answer:

pathwayschurch.com nameserver = NS1.GIGDEV.com

pathwayschurch.com nameserver = NS1.pathwayschurch.com

pathwayschurch.com nameserver = NS1.GIGDEV.com

pathwayschurch.com nameserver = NS1.pathwayschurch.com

NS1.GIGDEV.com internet address = 64.81.61.196

NS1.pathwayschurch.com internet address = 67.117.134.134

> set type=mx

> pathwayschurch.com

Server: adsl-67-117-134-134.dsl.snfc21.pacbell.net

Address: 67.117.134.134

*** adsl-67-117-134-134.dsl.snfc21.pacbell.net can't find pathwayschurch.com: No

n-existent domain

>

Can you please help me out. I am stumped and frustrated.

Thank you very much for your support

RE: DNS not resolving

It would probably help here is you could list the contents of the actual zone file.  On a Windows server it should be in \WINNT\system32\dns.  Most likely it will be named Pathwayschurch.com.dns.  

RE: DNS not resolving

(OP)
No problem ststokes. Here you go.

;
;  Database file pathwayschurch.com.dns for pathwayschurch.com zone.
;      Zone version:  17
;

@                       IN  SOA server01.pathwayschurch.com.  admin.pathwayschurch.com. (
                            17           ; serial number
                            900          ; refresh
                            600          ; retry
                            86400        ; expire
                            3600       ) ; minimum TTL

;
;  Zone NS records
;

@                       NS    server01.pathwayschurch.com.

;
;  Zone records
;

@                       A    67.117.134.134
pathwayschurchcom       A    67.117.134.134
                        MX    10    server01.pathwayschurch.com.
server01                A    67.117.134.134
                        A    192.168.254.2
www                     A    67.117.134.134
                        A    192.168.254.2

RE: DNS not resolving

(OP)
I'm sorry. I saw some errors with my recent changes. Here is the latest config.

;
;  Database file pathwayschurch.com.dns for pathwayschurch.com zone.
;      Zone version:  20
;

@                       IN  SOA server01.pathwayschurch.com.  admin.pathwayschurch.com. (
                            20           ; serial number
                            900          ; refresh
                            600          ; retry
                            86400        ; expire
                            3600       ) ; minimum TTL

;
;  Zone NS records
;

@                       NS    server01.pathwayschurch.com.

;
;  Zone records
;

@                       A    67.117.134.134
@                       MX    10    server01.pathwayschurch.com.
server01                A    67.117.134.134
                        A    192.168.254.2
www                     A    67.117.134.134
                        A    192.168.254.2

RE: DNS not resolving

Okay, don't ask me why but I had a heck of a time getting the MX record to read properly on my Win2K server when I recreated this.    Which is probably why I use Linux and BIND for everything except internal AD DNS.

Below is the copy of the zone record that I created that does work.  The only thing that I can point out is that you should remove the entries for the 192.168.254.x entries for the hosts.  That can get things a little confused at times.  Especially if an outside person gets that IP.

;
;  Database file Pathwayschurch.com.dns for pathwayschurch.com zone.
;      Zone version:  25
;

@                       IN  SOA server01.pathwayschurch.com.  admin.pathwayschurch.com. (
                            25           ; serial number
                            900          ; refresh
                            600          ; retry
                            86400        ; expire
                            3600       ) ; minimum TTL

;
;  Zone NS records
;

@                       NS    server01.pathwayschurch.com.

;
;  Zone records
;

@                       A    67.117.134.134
@                       MX    10    server01.pathwayschurch.com.
server01                A    67.117.134.134
www                     A    67.117.134.134


I hope this helps you because it confused the heck outta me.  

Scott  

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close