Reseller Hosting, Shared Hosting, Dedicated Hosting by Vortech Inc.

Go Back   Reseller Hosting, Shared Hosting, Dedicated Hosting by Vortech Inc. > >> General Public > H-Sphere Pre-Sales
User Name
Password
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

H-Sphere Pre-Sales Post your questions about H-Sphere plans here.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 11-06-2003, 10:37 AM
eCon's Avatar
eCon eCon is offline
Registered User
Junior Member
 
How to Validate MX record Prior DNS Change.

I have a domain (zotefoams-usa.com)created on a shared IP.
-We are hosting the mail at the end users facility.
-We have turned the Mail Service OFF.
-We added an MX record that point to the offsite IP in the DNS configuration settings.

Is seems we should be able to query our nameserver aliase(ns2.onlinessl.net)to see that the MX record exist(even though it is not the authoritative record.)

The query from dnsstuff.com shows only data from the current host.

We want to be sure that everything is configured correctly prior to making the authoritative record change at the registrar level.

Any suggestions?
Reply With Quote
  #2  
Old 11-06-2003, 05:37 PM
Brangwyn Brangwyn is online now
T3CHN0 STUD
Vortech Inc. Customer
 
Location: New Zealand (Wellington)
http://216.157.132.76/uploads/dnsview.zip

Last edited by Brangwyn : 06-17-2006 at 04:38 PM.
Reply With Quote
  #3  
Old 11-07-2003, 08:59 AM
eCon's Avatar
eCon eCon is offline
Registered User
Junior Member
 
Thank you. That is a great tool. I still can't seem to get comfortable with the results and am therefore hesitant to launch the site on this server.

- I can query current DNS info on NS and NS1. I get no results from NS2 and NS3. The TTL is 1 day. Should have propogated by now. Am I missing something?

- I don't understand how the domain level control in H-sphere handles the MX record once we point the domain to our nameserver. Is a record change sent out by this DNS function in H-sphere?

-It is a scary thought when you have the potential to shut down a large companies email. :-0
Reply With Quote
  #4  
Old 11-07-2003, 09:51 AM
mresell's Avatar
mresell mresell is offline
ePerson
Vortech Inc. Customer
 
Location: Around the \bin
putting a number in that is less than 10 for the mx record is important. Apparently 10 or above is where hsphere's built in records take over. So the other mx record may not get looked at properly. Also it can take more than 24hrs depending on where queries are being done.
Reply With Quote
  #5  
Old 11-07-2003, 07:24 PM
Brangwyn Brangwyn is online now
T3CHN0 STUD
Vortech Inc. Customer
 
Location: New Zealand (Wellington)
Quote:
Thank you. That is a great tool.
Your welcome

Actually most Windows OS'es have something similar built in as well, its a command called "nslookup"

If you open a command window (cmd) and type nslookup and hit enter it will go into interactive mode

Then enter the command "set type=all" hit enter
Then just enter the domain name you want to check i.e example.com and it will return the dns info

type "help" at any time in interactive mode to get more commands.

What mresell said about MX records is right, the priority is used to determine which order a sending mailserver will try to send mail too, an MX < 10 will put it with a higher priority than the Vortech mailserver which H-Sphere usually creates with a priority of 10
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
MX Record, Where to set it? bobi H-Sphere Pre-Sales 10 11-30-2003 02:03 PM


All times are GMT -5. The time now is 12:48 AM.


Powered by vBulletin Version 3.5.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Vortech Inc. ©2005
Page generated in 0.54485 seconds with 18 queries
[Output: 55.91 Kb. compressed to 52.21 Kb. by saving 3.70 Kb. (6.61%)]