voipwelcome.com

[usa2k]

C:\>ping in.usa2k.info

Pinging in.voipwelcome.com [67.228.177.9] with 32 bytes of data:
Reply from 67.228.177.9: bytes=32 time=61ms TTL=51
Reply from 67.228.177.9: bytes=32 time=61ms TTL=51
Reply from 67.228.177.9: bytes=32 time=63ms TTL=51
Reply from 67.228.177.9: bytes=32 time=62ms TTL=51

Ping statistics for 67.228.177.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 61ms, Maximum = 63ms, Average = 61ms

C:\>ping in.voipwelcome.com

Pinging in.voipwelcome.com [67.228.177.9] with 32 bytes of data:
Reply from 67.228.177.9: bytes=32 time=63ms TTL=51
Reply from 67.228.177.9: bytes=32 time=61ms TTL=51
Reply from 67.228.177.9: bytes=32 time=63ms TTL=51
Reply from 67.228.177.9: bytes=32 time=61ms TTL=51

Ping statistics for 67.228.177.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 61ms, Maximum = 63ms, Average = 62ms

Thank you for the education!

I tried a test on a URL that is unused and unrelated to the Reseller Account to see how your suggestion would work

Ping gives away the redirection very easily. Did I miss anything, or is the idea, that few people would try and ping the URL? At DSLReports.com people routinely check to see how they look in response time from the company they may decide on.

You could do all of the above from your end.

Example

Option 1
Using CNAME on your DNS
Domain: usa2k.com

CNAME: sip -> Address: sip-byod.voipwelcome.com

This allows you to use sip.usa2k.com address and if Tim changes the IP, you don't have to worry since it points to his name record and not IP.

Option 2
using "A" record on your DNS
Domain usa2k.com

A Record: 67.228.77.18

This allows you to use sip.usa2k.com and look like you own the server at a glance. Reverse look up still reveals sip-byod.voipwelcome.com but you cant change that. This is a common method in virtual and hosted server space.

Draw back is, if Tim changes his IP, you need to update that IP on your DNS entry.

sip-byod.voipwelcome.com and sip.voipwelcome.com shows up as an A record however the reverse look up comes back with sip-byod.voipwelcome.com. So for CNAME, i would recommend using sip-byod.voipwelcome.com but for A record, it doesn't matter since the DNS entry is an IP.

sip-byod.voipwelcome.com IN A 67.228.77.18 3600s (1h)
sip.voipwelcome.com IN A 67.228.77.18 3600s (1h)

Hope this helps,
M

[usa2k]

OK. Setting the A record to the voipwelcome.com IP
And the CNAME for 'in' to '@'
Then ping looks to belong to my URL.

Test call to sip:5551234444@in.usa2k.info
(Use your VOIPo number in place, seems to work interchangeably.)

The only thing is a dedicated URL is needed because the A record assignment is part of the disguise.

This is not perfect. If the A record points to the IP for in.voipwelcome.com
It does not seem possible to also point at the IP for sip.voipwelcome.com

sip.voipwelcome.com
in.voipwelcome.com
voipwelcome.com
All resolve to different IPs.

C:\>ping in.voipwelcome.com

Pinging in.voipwelcome.com [67.228.177.9] with 32 bytes of data:
Reply from 67.228.177.9: bytes=32 time=63ms TTL=51
Reply from 67.228.177.9: bytes=32 time=61ms TTL=51
Reply from 67.228.177.9: bytes=32 time=63ms TTL=51
Reply from 67.228.177.9: bytes=32 time=62ms TTL=51

Ping statistics for 67.228.177.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 61ms, Maximum = 63ms, Average = 62ms

C:\>ping in.usa2k.info

Pinging usa2k.info [67.228.177.9] with 32 bytes of data:
Reply from 67.228.177.9: bytes=32 time=63ms TTL=51
Reply from 67.228.177.9: bytes=32 time=63ms TTL=51
Reply from 67.228.177.9: bytes=32 time=63ms TTL=51
Reply from 67.228.177.9: bytes=32 time=63ms TTL=51

Ping statistics for 67.228.177.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 63ms, Maximum = 63ms, Average = 63ms