ZeroTier Question
-
Sure - any specific commands?
If not, I get:
Default Server: Unkown
Address: 2602:306:8b7e:f60::1 -
Let me ask this question...
We are a subdomain of the main branch organization. They have rmoved to Office 365 but we cannot be a part of that move. Don't get me started on that part.
Could this be part of the issue?
I don't see how but at this point I am looking at everything.
-
@WLS-ITGuy said in ZeroTier Question:
Sure - any specific commands?
If not, I get:
Default Server: Unkown
Address: 2602:306:8b7e:f60::1nslookup servername
If that returns nothing, check your DNS settings. What server is it trying to reach?
-
@WLS-ITGuy said in ZeroTier Question:
Let me ask this question...
We are a subdomain of the main branch organization. They have rmoved to Office 365 but we cannot be a part of that move. Don't get me started on that part.
Could this be part of the issue?
I don't see how but at this point I am looking at everything.
O365 doesn't have any components that would be involved here.
-
@WLS-ITGuy said in ZeroTier Question:
Default Server: Unkown
This implies that there is no default DNS server listed on that host. Is that right?
-
@Dashrender said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
Default Server: Unkown
This implies that there is no default DNS server listed on that host. Is that right?
Looks like that to me.
-
@scottalanmiller said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
Let me ask this question...
We are a subdomain of the main branch organization. They have rmoved to Office 365 but we cannot be a part of that move. Don't get me started on that part.
Could this be part of the issue?
I don't see how but at this point I am looking at everything.
O365 doesn't have any components that would be involved here.
Let me explain a bit.
www.wels.net is the main org
www.wls.wels.net is us.
The main org went Azure and Office 365 but due to costs we weren't going to move to office 365.
Could it have something to do with their DNS of www.wels.net being pointed to Office 365?
-
Show us the output of
ipconfig /all?
-
@WLS-ITGuy said in ZeroTier Question:
@scottalanmiller said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
Let me ask this question...
We are a subdomain of the main branch organization. They have rmoved to Office 365 but we cannot be a part of that move. Don't get me started on that part.
Could this be part of the issue?
I don't see how but at this point I am looking at everything.
O365 doesn't have any components that would be involved here.
Let me explain a bit.
www.wels.net is the main org
www.wls.wels.net is us.
The main org went Azure and Office 365 but due to costs we weren't going to move to office 365.
Could it have something to do with their DNS of www.wels.net being pointed to Office 365?
That would depend, but only in so much as finding things for Outlook setting itself up to find Exchange, etc, activesync for phones. It won't affect DNS itself for finding servers inside your organization.
-
Are their email address - [email protected]
and your email address - [email protected]?If so, those are two different DNS MX records. They can each go anywhere you want them to.
-
@dafyre said in ZeroTier Question:
Show us the output of
ipconfig /all?
http://i.imgur.com/4KvbqJ0.png
http://i.imgur.com/Q8orjss.png -
@Dashrender said in ZeroTier Question:
Are their email address - [email protected]
and your email address - [email protected]?If so, those are two different DNS MX records. They can each go anywhere you want them to.
That is correct. Exchange works fine as it is. I was just wondering if *.wels.net was getting sucked into Office 365 somehow.
We have noticed a few issues with people who are trying to access their Microsoft Accounts getting errors saying that there is no account for them at WELS Cloud.
-
@WLS-ITGuy said in ZeroTier Question:
@Dashrender said in ZeroTier Question:
Are their email address - [email protected]
and your email address - [email protected]?If so, those are two different DNS MX records. They can each go anywhere you want them to.
That is correct. Exchange works fine as it is. I was just wondering if *.wels.net was getting sucked into Office 365 somehow.
We have noticed a few issues with people who are trying to access their Microsoft Accounts getting errors saying that there is no account for them at WELS Cloud.
I would think in your case, you wouldn't want to have a *.wels.net record because of problems like this.
-
@Dashrender said in ZeroTier Question:
@WLS-ITGuy said in ZeroTier Question:
@Dashrender said in ZeroTier Question:
Are their email address - [email protected]
and your email address - [email protected]?If so, those are two different DNS MX records. They can each go anywhere you want them to.
That is correct. Exchange works fine as it is. I was just wondering if *.wels.net was getting sucked into Office 365 somehow.
We have noticed a few issues with people who are trying to access their Microsoft Accounts getting errors saying that there is no account for them at WELS Cloud.
I would think in your case, you wouldn't want to have a *.wels.net record because of problems like this.
Sorry - I meant the * as wls.wels.net
-
@Dashrender said in ZeroTier Question:
Sounds like you have a DNS issue. You might not be able to use short NetBIOS type names.. you might have to move to FQDN instead.
For example, if you're at StarBucks and the DHCP server gives a suffix of starbucks.com out with the IP, and you ping server1, your system might be pinging server1.starbucks.com instead of server1.yourdomain.com
I missed this or it didn't click. So you're saying that I might have to go to wls-dc01.wls.wels.net instead of WLS-DC01, correct?
-
Also, if I ping another server from off site I get this:
-
You need to go into the NIC settings for your ZT adapter and specify the ZT IP address of you internal DNS server...
What is happening is your ping / nslookup from off-site is using whatever DNS servers your ISP gives you.
Both of the IP addresses that I pointed to are the ZT IP addresses of my internal DNS servers.
-
@dafyre said in ZeroTier Question:
You need to go into the NIC settings for your ZT adapter and specify the ZT IP address of you internal DNS server...
What is happening is your ping / nslookup from off-site is using whatever DNS servers your ISP gives you.
Both of the IP addresses that I pointed to are the ZT IP addresses of my internal DNS servers.
DUDE! YOU ARE A GENIUS! <---Absoluetely no sarcasm
-
@WLS-ITGuy said in ZeroTier Question:
@dafyre said in ZeroTier Question:
You need to go into the NIC settings for your ZT adapter and specify the ZT IP address of you internal DNS server...
What is happening is your ping / nslookup from off-site is using whatever DNS servers your ISP gives you.
Both of the IP addresses that I pointed to are the ZT IP addresses of my internal DNS servers.
DUDE! YOU ARE A GENIUS! <---Absoluetely no sarcasm
This goes back to what I was saying earlier though... Your AD servers may have two IP addresses for everything... so if you ping ad01.mydomain.net, you might get the internal IP address... and that is fine if you are on site.
If you are off-site and your DNS server returns the internal IP, stuff still ain't gonna work.
Edit: Thanks for the Kudos.
-
@dafyre I got the onsite vs offsite part. However, shouldn't ZeroTier handle the offsite routing? Or is that not how this works
