Home / user-317984

amoreno's questions

Martin Hope
amoreno
Asked: 2019-01-16 16:20:40 +0800 CST
  • 0

We have a Windows 2016 server with the hostname, foo.example.com.

When logged into it as a Domain Admin, if we enter itself as a UNC path in Windows Explorer...

\\foo.example.com\d$

...we can access it.

Same if we use localhost or it's IP.

However, if we use another DNS A record for the same IP, let's say bar.example.com, we get prompted for Administrative credentials.

AND if we enter correct credentials, we get a The specified network password is not correct.

What are we doing wrong?

UPDATE: Something else I should've mentioned is that this issue only occurs when on the server itself. If I navigate to the alternate A record (NOTE: not a CNAME...if that matters) across the network, it works fine.

windows
Martin Hope
amoreno
Asked: 2016-06-07 14:00:01 +0800 CST
  • 5

so we're a University campus, and in DNS Manager, all the students phones, tables, etc, are registering their A records in DNS. We don't want them to. Ideally, we'd just have domain joined devices registering/updating their DNS records.

We've done the following:

  • DNS: Right click on domain in fwd lookup zone > Properties > Changed "Dynamic Updates" to "Secure only." (it was previously "Nonsecure and secure")
  • DHCP: Right click the respective DHCP Scope > Properties > DNS Tab > UNCHECK "Enable DNS dynamic updates according to the settings below"
  • DNS: Delete all records from the student subnets (from every DNS server)

It seemed like it was working for a little while, but then every hour, on the hour, I start to see old records repopulate Windows DNS Manager.

What are we missing? The main push for this was, we had a DNS Squatting issue, where a student's phone's hostname was the same as one of our servers, which prevented end users from accessing that server via the DNS name. Temporary mitigation was to create a CNAME for it, as it appears Dynamic Updates don't update CNAMEs, but we'd ideally like to prevent all non-domain joined devices from registering in DNS.

Thanks in advance.

domain-name-system internal-dns dns-zone dynamic-dns
Martin Hope
amoreno
Asked: 2015-11-10 15:07:12 +0800 CST
  • 1

Short version: mounted datasets are RO, even though I'm trying to make them RW.

Long version: we currently have a working implementation of ZFS on Linux on Wheezy (which I inherited when the previous SE left) and we want to upgrade to Jessie...because...just because. Before upgrading production, I'm trying to replicate that environment (as much as possible) in a VM running on my local machine.

I've created the pool, and created a new dataset via:

root@zfstest1:~# zfs set [email protected],insecure tank/vmware
root@zfstest1:~# zfs share -a
root@zfstest1:~# showmount -e

Export list for zfstest1:
/tank/vmware 10.1.2.3

I've compared permissions and properties and everything that I can think of against production, but regardless of whether I mount the datasets on my Mac or on a VMware host, the volume/datastore ends up being RO. Default permissions for /tank and child objects appears to be 755, and the only way I've found to make the mounted volumes on my Mac or VMware host RW, is to make them 777.

Some things that I know are different are the different zfs-debian, spl-dkms, etc packages. I just couldn't find the repository to get older ones (0.6.3-1~wheezy vs 0.6.5.2-2-wheezy)

Help on what I can look for to get this working would be greatly appreciated.

debian